Systems and Methods for Correlating Meta-Data Model Representations and Asset-Logic Model Representations

ABSTRACT

Systems and methods for correlating meta-data model representations and asset-logic model representations in a system model. The system model may be deployed in conjunction with a production allocation application, whereby data pertaining to allocation changes to a production system might be more readily identified for different purposes such as, for example, technical and/or fiscal allocation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/418,367, filed on Apr. 3, 2009, claims the priority of U.S. PatentApplication 61/042,542, filed Apr. 4, 2008, which are both incorporatedherein by reference.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH

Not applicable.

FIELD OF THE INVENTION

The present invention generally relates to correlating meta-data modelrepresentations and asset-logic model representations in a system model.

BACKGROUND OF THE INVENTION

Understanding and operating an oil and gas production asset as a singleholistic system has been frustrated by significant impediments. For anyasset, there are typically multiple applications, multiple data sets,multiple taxonomies and multiple stakeholders, some or all of which maybe sharing common data across the asset. Interoperability among theseprograms, persons, and structures as a single system, while desired, hasbeen frustrated by the lack of an underlying framework for handling thenecessary transformations, translations, and definitions requiredbetween and among the various system components.

Attempts to provide this understanding and operation have previouslyfocused on providing data replication, where each stakeholder groupdevelops or receives its own version of the logical network and datamodel that includes all of its requirements. In these attempts, the actof transforming the data model by correlating changes between the datamodel representations has not been done or has been done crudely.Although some level of interoperability has been achieved by point topoint integration, it is largely limited to supporting single workflows.Moreover, changes to the data model representations cannot beeffectively controlled when each stakeholder can decide whether suchchanges should be applied (accepted) and communicated to the otherstakeholders. Previous approaches thus, have been unable to account forreconciliation and data integrity issues in a systematic and/orsystem-wide way.

There is therefore, a need for systems and methods that provideuninterrupted interoperability among the various data sets,applications, taxonomies and stakeholders sharing data across aproduction asset. In other words, there is a need for transforming asystem model by correlating only approved manipulations of meta-datamodel representations and asset-logic model representations in thesystem model.

SUMMARY OF THE INVENTION

The present invention therefore, meets the above needs and overcomes oneor more deficiencies in the prior art by providing systems and methodsfor correlating only approved manipulations of meta-data-modelrepresentations and asset-logic model representations in a system model.

In one embodiment, the present invention includes a method forcorrelating meta-data model representations and asset-logic modelrepresentations, which comprises: i) manipulating a system model, thesystem model comprising a meta-data model representation and anasset-logic model representation; ii) recording each manipulationapproved or rejected by only at least one stakeholder and anotherstakeholder; and iv) transforming the system model on a computer systemby correlating only each approved manipulation between the meta-datamodel representation and the asset-logic model representation.

In another embodiment, the present invention includes a non-transitoryprogram carrier device tangibly carrying computer executableinstructions for correlating meta-data model representations andasset-logic model representations. The instructions are executable toimplement: i) manipulating a system model, the system model comprising ameta-data model representation and an asset-logic model representation;ii) recording each manipulation approved or rejected by only at leastone of the stakeholder and another stakeholder; and iv) transforming thesystem model by correlating only each approved manipulation between themeta-data model representation and the asset-logic model representation.

In yet another embodiment, the present invention includes a computerreadable medium carrying computer executable instructions forcorrelating meta-data model representations and asset-logic modelrepresentations, the computer readable medium comprising: i) a systemmodel, the system model comprising a meta-data model representation andan asset-logic model representation; ii) a recording module forrecording each manipulation approved or rejected by only at least one ofa stakeholder and another stakeholder; and iv) a transformation modulefor transforming the system model by correlating only each approvedmanipulation between the meta-data model representation and theasset-logic model representation.

Additional aspects, advantages and embodiments of the invention willbecome apparent to those skilled in the art from the followingdescription of the various embodiments and related drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described below with references to theaccompanying drawings in which like elements are referenced with likereference numerals, and in which:

FIG. 1 is a block diagram illustrating a system for implementing thepresent invention.

FIG. 2 illustrates the collaborative network matrix model of the presentinvention in relation to a wider system for collaboration.

FIG. 3 is a block diagram illustrating the collaborative network matrixmodel in FIG. 2.

FIG. 4 is a block diagram illustrating the collaborative network matrixmodel in FIG. 2 after a system change.

FIG. 5 is a block diagram illustrating the collaborative network matrixmodel in FIG. 2 as a transformation.

FIG. 6 illustrates the development and change of a collaborative networkmatrix model over time.

FIG. 7 is a flow diagram illustrating one embodiment of a method forimplementing the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The subject matter of the present invention is described withspecificity, however, the description itself is not intended to limitthe scope of the invention. The subject matter thus, might also beembodied in other ways, to include different steps or combinations ofsteps similar to the ones described herein, in conjunction with otherpresent or future technologies. Moreover, although the term “step” maybe used herein to describe different elements of methods employed, theterm should not be interpreted as implying any particular order among orbetween various steps herein disclosed unless otherwise expresslylimited by the description to a particular order. While the followingdescription refers to the oil and gas industry, the systems and methodsof the present invention are not limited thereto and may also be appliedto other industries to achieve similar results.

The present invention provides a model based solution to select theappropriate level of model detail for the preferences of dissimilarusers, also referred to herein as clients or stakeholders. Unlike theprior art, the present invention correlates different models. Thus, thepresent invention permits moving between models with different levels ofdetail. Moreover, while different models with various levels of detailmay be known in the art, the present invention, instead, provides theopportunity to utilize different models in a single application witheach model related to a common system model.

System Description

The present invention may be implemented through a computer-executableprogram of instructions, such as program modules, generally referred toas software applications or application programs executed by a computer.The software may include, for example, routines, programs, objects,components, and data structures that perform particular tasks orimplement particular abstract data types. The software forms aninterface to allow a computer to react according to a source of input.DecisionSpace®, which is a commercial software application marketed byLandmark Graphics Corporation, may be used as an interface applicationto implement the present invention. The software may also cooperate withother code segments to initiate a variety of tasks in response to datareceived in conjunction with the source of the received data. Thesoftware may be stored and/or carried on any variety of memory mediasuch as CD-ROM, magnetic disk, bubble memory and semiconductor memory(e.g., various types of RAM or ROM). Furthermore, the software and itsresults may be transmitted over a variety of carrier media such asoptical fiber, metallic wire, free space and/or through any of a varietyof networks such as the Internet.

Moreover, those skilled in the art will appreciate that the inventionmay be practiced with a variety of computer-system configurations,including hand-held devices, multiprocessor systems,microprocessor-based or programmable-consumer electronics,minicomputers, mainframe computers, and the like. Any number ofcomputer-systems and computer networks are acceptable for use with thepresent invention. The invention may be practiced indistributed-computing environments where tasks are performed byremote-processing devices that are linked through a communicationsnetwork. In a distributed-computing environment, program modules may belocated in both local and remote computer-storage media including memorystorage devices. The present invention may therefore, be implemented inconnection with various hardware, software or a combination thereof, ina computer system or other processing system.

Referring now to FIG. 1, a block diagram of a system for implementingthe present invention on a computer is illustrated. The system includesa computing unit, sometimes referred to as a computing system, whichcontains memory, application programs, a client interface, and aprocessing unit. The computing unit is only one example of a suitablecomputing environment and is not intended to suggest any limitation asto the scope of use or functionality of the invention.

The memory primarily stores the application programs, which may also bedescribed as program modules containing computer-executableinstructions, executed by the computing unit for implementing thepresent invention described herein and illustrated in FIGS. 2-7. Thememory therefore, includes a CNMM Module, which enables the methodillustrated and described in reference to FIG. 7. The CNMM Moduleincludes a collaborative-network-matrix model, also known as a systemmodel, which is illustrated and described in reference to FIGS. 2-7. TheCNMM Module also may interact with DecisionSpace®, AssetObserver™,AssetSolver™ and AssetConnect™ as further described in reference to FIG.2. The systems and methods of the present invention are thus, based on asystem model that correlates meta-data-model representations of aproduction asset with the various asset-logic model representations (ortaxonomies) to provide a collaborative, consistent, and relevantrepresentation of the asset to the different stakeholders. The systemmodel performs the correlations between different meta-data modelrepresentations using the various asset-logic model representations forcommon data items and attributes shared across the system thus,addressing the many key activities relating to the asset that may havedifferent meta-model representations representing their pertinent datarequirements. In this manner, effective interoperability is achieved.

Although the computing unit is shown as having a generalized memory, thecomputing unit typically includes a variety of computer readable media.By way of example, and not limitation, computer readable media maycomprise computer storage media and communication media. The computingsystem memory may include computer storage media in the form of volatileand/or nonvolatile memory such as a read only memory (ROM) and randomaccess memory (RAM). A basic input/output system (BIOS), containing thebasic routines that help to transfer information between elements withinthe computing unit, such as during start-up, is typically stored in ROM.The RAM typically contains data and/or program modules that areimmediately accessible to and/or presently being operated on by theprocessing unit. By way of example, and not limitation, the computingunit includes an operating system, application programs, other programmodules, and program data.

The components shown in the memory may also be included in otherremovable/nonremovable, volatile/nonvolatile computer storage media. Forexample only, a hard disk drive may read from or write to nonremovable,nonvolatile magnetic media, a magnetic disk drive may read from or writeto a removable, non-volatile magnetic disk, and an optical disk drivemay read from or write to a removable, nonvolatile optical disk such asa CD ROM or other optical media. Other removable/non-removable,volatile/non-volatile computer storage media that can be used in theexemplary operating environment may include, but are not limited to,magnetic tape cassettes, flash memory cards, digital versatile disks,digital video tape, solid state RAM, solid state ROM, and the like. Thedrives and their associated computer storage media discussed abovetherefore, store and/or carry computer readable instructions, datastructures, program modules and other data for the computing unit.

A client may enter commands and information into the computing unitthrough the client interface, which may be input devices such as akeyboard and pointing device, commonly referred to as a mouse, trackballor touch pad. Input devices may include a microphone, joystick,satellite dish, scanner, or the like.

These and other input devices are often connected to the processing unitthrough the client interface that is coupled to a system bus, but may beconnected by other interface and bus structures, such as a parallel portor a universal serial bus (USB). A monitor or other type of displaydevice may be connected to the system bus via an interface, such as avideo interface. In addition to the monitor, computers may also includeother peripheral output devices such as speakers and printer, which maybe connected through an output peripheral interface.

Although many other internal components of the computing unit are notshown, those of ordinary skill in the art will appreciate that suchcomponents and their interconnection are well known.

Referring now to FIG. 2, a collaborative-network-matrix model (systemmodel 214) is illustrated within a wider system 200 for collaborationamong multiple clients referred to as stakeholders 218. Additionalsystem components typically associated with a production asset mayinclude, for example, different types of data 202 (e.g. operations data,business data and engineering data), a data analytics engine 204, a dataintegration platform 206, a data environment 208, a workflow integrationplatform 210, a software applications environment 212 and acollaborative environment 216. The various components of the system 200enable specific inter-related functions and therefore, must interactwith each other seamlessly in order to avoid discontinuities and/orerrors. The role of the system model 214 is to provide interoperabilityacross the various diverse applications and datasets within the overallsystem 200. Thus, the system model 214 functions as a common base modelfor collaboration among the stakeholders 218. Other components of thesystem 200 may include interfaces to and from an Enterprise ResourcePlanning System (e.g. SAP) or a computerized Maintenance ManagementSystem, or a computerized Work Management System controlling work in thephysical asset and necessary status of equipment and system isolations.

The data analytics engine 204 allows data to be manipulated to producenumerous reports and analysis using simple to complex proprietary andindustry standard algorithms. It typically supports data filtering andcleaning as well as appropriate visualization technologies to presentdata in meaningful, relevant and insightful ways into the viewing orcollaborative environment 216 for use by the stakeholders 218.

The data integration platform 206 typically provides data connectorsappropriate to each data language and database. This component allowsthe stakeholders 218 to map to particular data sets such as assetequipment tags or unique well identifiers, thus enabling data flowthroughout the system 200.

The data environment 208 typically interfaces with some regulatory ordistributed control system incorporating data to and from instruments,meters, and control devices, such as actuators, valves and the like,across the asset. Considering the typical functions of each component,the data environment 208 typically includes multiple types of data 202,each designed to best suit particular types of data. For example, arelational database for business data, a data historian for highfrequency operations data and a data warehouse for engineering data suchas well tables and production allocation tables. The data will exist inone or more data languages, such as, for example, OPC, ODBC, HTML,WITSML, and PRODML, which are well known in the art and conform torespective corresponding data standards.

The workflow integration and orchestration platform 210 spans thevarious IT operating environments, connects to the numerous softwareapplications, maps to the respective data tags and items used by thesoftware applications and interfaces with some viewing or sharedcollaborative environments to interface and interact with numerousstakeholders 218 involved across the workflows. The workflows arenumerous but might include frequent and infrequent activities such as,for example, well test validation, production allocation, productionsurveillance, production optimization and others more particularlydescribed in U.S. patent application Ser. No. 12/266,766, which isincorporated herein by reference.

The software applications environment(s) 212 includes different IToperating environments such as Windows and Linux, appropriate to therange of applications used across the asset. The software applicationsenvironment(s) 212 may also include well known, proprietary applicationsfor providing diverse, complex, and relatively simple functionality.These applications, for example, may include petro-technical andgeoscience applications common to the industry as well as more commonsoftware applications commonly used such as MS Office. Theseapplications may also be used for, but not limited to, reservoir andwell simulation, modeling of hydraulic networks and facilities systems,material balance, nodal analysis, production allocation, productionsurveillance, hydrocarbon accounting, regulatory reporting, andeconomics. These applications may be proprietary or customized and willinvariably incorporate and use a multitude of algorithms, units, andannotations. These applications will also manipulate, and transformexisting data and generate further data in ways unique to theapplications.

The function of the system model 214 is to manage the numerousinterfaces and interactions between the data items and their correct andconsistent usage within the various logic schemes that arerepresentative of the system 200 and its architecture. It does so in adynamic operating environment where all or many of the components may beused simultaneously and/or continuously by the stakeholders 218, whichmay be given specific and varying access and authority rights to controlthe components.

The collaborative environment 216 typically represents a web-based(intranet or internet) access and viewing environment that can be usedby a diverse range of potential geographically located stakeholders 218,which will provide secure access and bandwidths appropriate to the rangeof data and software applications included in the system 200. The use ofportals will typically allow diverse stakeholders 218 to have relevantcustom views of only the information they require from the system 200and also may provide effective communications via e-mail, instantmessaging, net meetings and the like.

DecisionSpace® for Production may be used to provide the systemarchitecture, component integration and set of functionality illustratedin FIG. 2. The system model 214, however, interacts with AssetObserver™,AssetConnect™ and AssetSolver™ to achieve overall functionality.AssetObserver™ provides the data integration platform 206 and also thecollaborative environment 216 for data organization and visualizationwithin the overall system 200. AssetConnect™ provides the softwareapplication environment(s) 212 and also the workflow integrationplatform 210, which, together, enable orchestration or technicalworkflows that utilize both technical applications and related data 202.AssetSolver™ provides the data analytics engine 204, which is capable ofhandling both high volume and real-time data about operations andaggregate historical data used for engineering purposes. Each of thecomponents jointly and separately benefit from the functionalityprovided by the system model 214.

Referring now to FIG. 3, a block diagram of thecollaborative-network-matrix model in FIG. 2 (system model 214) isillustrated. Initially, the system model 214 is static, meaning at rest,when transformations and manipulations are not occurring. During thistime period, the system model 214 acts purely as a data router—providingthe flow of appropriate information to different organizationalstakeholders and/or applications. The system model 214 includes severalcomponents, such as the vertical components L1-LN, the horizontalcomponents M1-MN, transformations and manipulations.

The vertical components L1-LN may include logical representations of thevarious taxonomies representative of the asset such as, for example,business logic, operations logic, engineering logic, scientific logicand organizational logic, among others. As illustrated in FIG. 3, thetaxonomies include scientific logic and business logic.

The horizontal components M1-MN are meta-data model representations ofspecific key activities or stakeholder domains or other manifestationsof meta-data model representations appropriate to the asset such as, forexample, production data, business data, engineering data and equipmentdata, among others. As illustrated in FIG. 3, the meta data modelrepresentations include operations, design, regulatory, meter, flow andphysical network. The meta-data model representations comprise numerousdata items and their attributes.

Transformations are the routines for definition, identification andcorrelation of data items and attributes within the meta-data modelrepresentation layers, which are shared across the various asset-logicmodel representations. This might include, for example, algorithms,rules, units, logic and data transfer language, among others. Routinesmay include, for example, initial screening, searching, comparison andmatching of the data items and attributes across the various componentsof the system model 214. Screening is an activity undertaken byproprietary software in order to identify the range of data attributesin the system model 214. Searching may involve a search engine to findthe locations of such attributes and a comparison may utilize artificialintelligence (such as a neural network or expert system) in order todetermine correlations and interrelationships between meta-data modelrepresentations and asset-logic model representations, across the systemmodel 214. This function allows translation of common data items andattributes between one meta-data model representation layer and others.

Manipulations are automatically initiated at occurrence of an event andmay include, for example: a) the various and multiple uses of data itemsand attributes across the asset by the multiple stakeholders using thediverse data sources, applications and programs common to a productionasset, b) the control or subsequent change of those relatively staticasset-logic model representations and meta-data model representationsand/or the correlations or attributes of data items therein such as, forexample: i) a permanent or temporary physical change to the productionsystem configuration by insertion or removal of an item of equipment,ii) a change on the organization structure and/or individuals in a givenrole or to their approval authority or iii) modification to anengineering algorithm, and c) the control or subsequent change of theasset-logic model representations, the meta-data model representationsand/or the correlations or attributes of data items therein such as, forexample: i) a change to a valve brought about by, and consistent with,well testing operations or shutdown of an item of equipment for plannedmaintenance routines, or ii) the routine change to a modeled assetcomponent, such as an inflow production ratio (IPR) curve, usedroutinely by production engineering.

Referring now to FIG. 4, a block diagram of thecollaborative-network-matrix model in FIG. 2 (system model 214) isillustrated after a system change. A first stakeholder such as, forexample, a production engineer may manipulate several horizontalcomponents to reflect a system change that has occurred. In other words,a system change reflects a manipulation of the operations, flow andphysical network meta-data model representations.

Referring now to FIG. 5, a block diagram of thecollaborative-network-matrix model in FIG. 2 (system model 214) isillustrated as a transformation. Between each horizontal component andacross the asset-logic model representations (vertical components),proprietary transformation routines are applied to appropriately accountfor the first stakeholder's manipulation-resulting in a system changeacross the system model 214. A change in any horizontal component mayalso effect change to other horizontal components and/or verticalcomponents affected by the change, subject to agreement and approval ofthe designated owner (stakeholder) in control of the impacted logic,meta-data model representation or data item. Variable data attributeswill not initiate change controls, which apply to only fixed ordetermined data items and attributes. The system model 214 is able todetermine which stakeholder or stakeholders need to be informed of thechanges to the horizontal components and/or vertical components and whoinitiated the change(s). This is achieved through an event notificationservice. The status of the components may be tracked during periods ofchange to ensure appropriate adjustment according to outcome of thesystem change controls. The system model 214 may be housed within a datarepository with real time audit control. This mechanism is utilized totrack component changes. Components of the system model 214 may bedesignated more or less critical at the establishment of the systemmodel 214 such that risk can be determined and communicated with alertsto the system stakeholders. The system model 214 may record rejected andapproved changes and effect resulting necessary transformations acrossthe system model 214. Approval's are generated either by humaninteraction with the system or by a logic based expert system.

Referring now to FIG. 6, the development and change of a collaborativenetwork matrix model over time is illustrated. Each iterative change iscaptured by the system and is fully auditable. Changes can includechanges to stakeholders, asset-logic model representations, meta-datamodel representations and/or data items and attributes.

Method Description

Referring now to FIG. 7, a flow diagram illustrates one embodiment of amethod 700 for implementing the present invention.

In step 702, a system model is created, which comprises one or moremeta-data model representations and one or more asset-logic modelrepresentations. The system model may include, for example, the samemeta-data model representations and/or asset logic model representationsdescribed in reference to FIGS. 2-5. Furthermore, the system model mayoperate, for example, in the same manner as the system model describedin reference to FIGS. 1-6. Each meta-data model representation may becontrolled by one or more respective stakeholders and each asset-logicmodel representation may be controlled (owned) by one or more respectivestakeholders. In other words, each meta-data model representation may becontrolled by a respective stakeholder and each asset-logic modelrepresentation may be controlled by a respective stakeholder.Optionally, any respective stakeholder may control more than onemeta-data model representation and/or more than one asset-logic modelrepresentation. Conversely, each meta-data model representation and eachasset-logic model representation should not be controlled by more thanone respective stakeholder however, may be controlled by more than onestakeholder under exceptional circumstances. Each meta-data modelrepresentation may include at least one data item and an attribute.Likewise, each asset-logic model representation may include at least onedata item and an attribute.

In step 704, the system model is manipulated using a GUI or other meanswell known in the art. A collaborative environment and/or API may beutilized within a wider system to facilitate manipulation of the systemmodel. The system model may be manipulated, for example, by amanipulation of one or more of the meta-data model representationsand/or one or more of the asset-logic model representations. Amanipulation therefore, may represent a change to at least one of themeta-data model representations and the asset-logic modelrepresentations. The system model may be manipulated on a computersystem by any stakeholder. Each stakeholder therefore, may access thesystem model through a collaborative environment to manipulate thesystem model on the computer system. Each stakeholder therefore, maycontrol one or more meta-data model representations and/or asset-logicmodel representations, while having access to the system model through acollaborative environment for purposes of manipulating the system model.Each stakeholder however, having access to the system model through acollaborative environment for purposes of manipulating the system modelmay not have control of one or more meta-data model representationsand/or asset-logic model representations.

In step 706, each stakeholder in control of the one or more meta-datamodel representations and/or the one or more asset-logic modelrepresentations is notified of a manipulation of each respectivemeta-data model representation and/or each respective asset-logic modelrepresentation controlled by each respective stakeholder. Acollaborative environment and/or API my be utilized within a widersystem to facilitate notification of each manipulation. In this manner,for example, a stakeholder may manipulate one or more of the meta-datamodel representations and/or one or more of the asset-logic modelrepresentations, which it does not control, and only each stakeholder incontrol of each respective manipulated meta-data model representationand/or asset-logic model representation is notified of the manipulation.

In step 708, each manipulation approved or rejected by each respectivestakeholder in control of the manipulated meta-data modelrepresentation(s) and/or asset-logic model representation(s) is recordedby the system model. Each approved manipulation therefore, may representa change to a data item and/or an attribute in one or more of themeta-data model representations and/or one or more of the asset-logicmodel representations.

In step 710, the system model is transformed on a computer system basedon the approved manipulation(s) by correlating each approvedmanipulation between the meta-data model representation(s) and theasset-logic model representation(s). Transforming the system modelcomprises using at least one routine for correlating each approvedmanipulation between the meta-data model representation(s) and theasset-logic model representation(s).

In step 712, the method 700 determines whether to repeat. If the method700 is repeated, then the method 700 proceeds to step 704. If the method700 does not repeat, then the method 700 ends.

The system model may be deployed in conjunction with a productionallocation application whereby data pertaining to allocation changes tothe production system might be more readily identified and for differingpurposes such as technically correct allocation and fiscal allocationfor operations, engineering and/or business uses. Other applicationsutilizing the system model may include, for example, production lossreporting, whereby the various causes of lost production might beattributed as they are reported, understood and associated with relevantoperations, engineering and business data and uses.

While the present invention has been described in connection withpresently preferred embodiments, it will be understood by those skilledin the art that it is not intended to limit the invention to thoseembodiments. It is therefore, contemplated that various alternativeembodiments and modifications may be made to the disclosed embodimentswithout departing from the spirit and scope of the invention defined bythe appended claims and equivalents thereof.

1. A method for correlating meta-data model representations andasset-logic model representations, which comprises: manipulating asystem model, the system model comprising a meta-data modelrepresentation and an asset-logic model representation; recording eachmanipulation of at least one of the meta-data model representation andthe asset-logic model representation approved or rejected by only atleast one of stakeholder and another stakeholder; and transforming thesystem model on a computer system by correlating only each approvedmanipulation between the meta-data model representation and theasset-logic model representation.
 2. The method of claim 1, wherein themanipulation of the at least one of the meta-data model representationand the asset-logic model representation represents a change to at leastone of the meta-data model representation and the asset-logic modelrepresentation.
 3. The method of claim 2, wherein the meta-data modelrepresentation comprises at least one of a data item and an attribute,and the asset-logic model representation comprises at least one of thedata item and the attribute.
 4. The method of claim 1, whereintransforming the system model comprises using at least one routine forcorrelating each approved manipulation between the meta-data modelrepresentation and the asset-logic model representation.
 5. The methodof claim 1, wherein each approved manipulation of the at least one ofthe meta-data model representation and the asset-logic modelrepresentation represents a change to at least one of a data item and anattribute in at least one of the meta-data model representation and theasset-logic model representation.
 6. The method of claim 1, furthercomprising: manipulating the system model, the system model comprisinganother meta-data model representation controlled by only a newstakeholder and another asset-logic model representation controlled byonly the new stakeholder or another new stakeholder; notifying only atleast one of the stakeholder, the another stakeholder, the newstakeholder and the another new stakeholder of a manipulation of atleast one of the meta-data model representation, the asset-logic modelrepresentation, the another meta-data model representation and theanother asset-logic model representation; recording each manipulationapproved or rejected by the at least one of the stakeholder, the anotherstakeholder, the new stakeholder and the another new stakeholder; andtransforming the system model by correlating only each approvedmanipulation between the meta-data model representation, the anothermeta-data model representation, the asset-logic model representation,and the another asset-logic model representation.
 7. The method of claim1, wherein the system model is manipulated by a new stakeholder and onlythe stakeholder is notified of a manipulation of the meta-data modelrepresentation and only the stakeholder or the another stakeholder isnotified of a manipulation of the asset-logic model representation. 8.The method of claim 1, wherein the system model is manipulated on thecomputer system by a new stakeholder.
 9. The method of claim 8, whereinthe stakeholder, the another stakeholder and the new stakeholder accessthe system model through a collaborative environment.
 10. Anon-transitory program carrier device tangibly carrying computerexecutable instructions for correlating meta-data model representationsand asset-logic model representations, the instructions being executableto implement: manipulating a system model, the system model comprising ameta-data model representation and an asset-logic model representation;recording each manipulation of at least one of the meta-data modelrepresentation and the asset-logic model representation approved orrejected by only at least one of stakeholder and another stakeholder;and transforming the system model by correlating only each approvedmanipulation between the meta-data model representation and theasset-logic model representation.
 11. The program carrier device ofclaim 10, wherein the manipulation of the at least one of the meta-datamodel representation and the asset-logic model representation representsa change to at least one of the meta-data model representation and theasset-logic model representation.
 12. The program carrier device ofclaim 11, wherein the meta-data model representation comprises at leastone of a data item and an attribute, and the asset-logic modelrepresentation comprises at least one of the data item and theattribute.
 13. The program carrier device of claim 10, whereintransforming the system model comprises using at least one routine forcorrelating each approved manipulation between the meta-data modelrepresentation and the asset-logic model representation.
 14. The programcarrier device of claim 10, wherein each approved manipulation of the atleast one of the meta-data model representation and the asset-logicmodel representation represents a change to at least one of a data itemand an attribute in at least one of the meta-data model representationand the asset-logic model representation.
 15. The program carrier deviceof claim 10, further comprising: manipulating the system model, thesystem model comprising another meta-data model representationcontrolled by only a new stakeholder and another asset-logic modelrepresentation controlled by only the new stakeholder or another newstakeholder; notifying only at least one of the stakeholder, the anotherstakeholder, the new stakeholder and the another new stakeholder of amanipulation of at least one of the meta-data model representation, theasset-logic model representation, the another meta-data modelrepresentation and the another asset-logic model representation;recording each manipulation approved or rejected by the at least one ofthe stakeholder, the another stakeholder, the new stakeholder and theanother new stakeholder; and transforming the system model bycorrelating only each approved manipulation between the meta-data modelrepresentation, the another meta-data model representation, theasset-logic model representation, and the another asset-logic modelrepresentation.
 16. The program carrier device of claim 10, wherein thesystem model is manipulated by a new stakeholder and only thestakeholder is notified of a manipulation of the meta-data modelrepresentation and only the stakeholder or the another stakeholder isnotified of a manipulation of the asset-logic model representation. 17.The program carrier device of claim 10, wherein the system model ismanipulated by a new stakeholder.
 18. The program carrier device ofclaim 17, wherein the stakeholder, the another stakeholder and the newstakeholder access the system model through a collaborative environment.19. A computer readable medium carrying computer executable instructionsfor correlating meta-data model representations and asset-logic modelrepresentations, the computer readable medium comprising: a systemmodel, the system model comprising a meta-data model representation andan asset-logic model representation; a recording module for recordingeach manipulation of at least one of the meta-data model representationand the asset logic model representation approved or rejected by only atleast one of a stakeholder and another stakeholder; and a transformationmodule for transforming the system model by correlating only eachapproved manipulation between the meta-data model representation and theasset-logic model representation.
 20. The computer readable medium ofclaim 19, wherein the system model is manipulated on the computer systemby a new stakeholder and the stakeholder, the another stakeholder andthe new stakeholder access the system model through a collaborativeenvironment.